Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) and too complex database calls.
• I strictly followed the principle of data economy for all database calls.
• I strictly followed the server coding and design guidelines.
• I added multiple integration tests (Spring) related to the features (with a high test coverage).
• I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
• I documented the Java code using JavaDoc style.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data (e.g. using paging).
• I strictly followed the principle of data economy for all client-server REST calls.
• I strictly followed the client coding and design guidelines.
• Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
• I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
• I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
• I documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes.
• I translated all newly inserted strings into English and German.

Motivation and Context

Resolves #9527

Description

This PR adds a subpage to the SSH settings, to let users display Artemis key fingerprints

Steps for Testing

1. Login and navigate to the SSH settings.
2. Click the fingerprints link
3. Verify the displayed fingerprint is correct (e.g. delete your known hosts file/remove the test server's entry, and use SSH to clone something)

Testserver States

Review Progress

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Test Coverage

Client

Server

Screenshots

(Shows fingerprints depending on which are configured for the server)

Summary by CodeRabbit

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a service for managing SSH fingerprints.
  • Added a REST controller for retrieving SSH fingerprints via a new API endpoint.
  • Implemented a user interface component for displaying SSH fingerprints in user settings.
  • Enhanced SSH settings with new routes for managing SSH keys and fingerprints.
  • Expanded user settings with new fields and error messages related to SSH key management.
  • Introduced automatic expiration settings for SSH keys.

• Bug Fixes

  • Improved error handling for SSH key management.

• Documentation

  • Updated user settings documentation with new error messages and details about SSH keys.

• Tests

  • Added comprehensive test suites for the new components and services related to SSH fingerprint management.
  • Established tests for the functionality of retrieving SSH fingerprints.